Agilent does not officially support the Agilent VISA IO Library controlling National Instrument's IO hardware, nor the NI-VISA IO Library controlling Agilent's IO hardware, except on the Agilent E9850A Embedded Controller.
We have had requests from customers wanting to mix National Instruments and
Agilent IO hardware and software. We realize that some of our customers need
these mixed environments to support new products from Agilent and NI. With VISA,
interoperability with mixed IO hardware and software is now easier. We expect
most of these mixed configurations to work. However, since these configurations
have not been thoroughly tested, we cannot officially support them at this time.
The only platform that officially supports a mixed environment is the Agilent
E9850A Embedded Controller.
This page describes the following:
How to configure a National Instruments GPIB card to work with the Agilent IO Libraries
To use an NI GPIB card with the Agilent IO Libraries, do the following:
If IO Config did not detect the presence of a configured NI-488 GPIB interface, you can override the default search algorithm and directly specify the configured NI-488 GPIB interfaces by creating and editing the intfcfg.ini so that IO Config can configure them.
Creating intfcfg.ini:
The intfcfg.ini file must be created. It is not installed by the Agilent IO Libraries installer. If you have not previously created intfcfg.ini, you can create it by copying the sample intfcfg.txt file to intfcfg.ini. intfcfg.txt is located in the intfcfg subdirectory under the Agilent IO Libraries installation directory:
c:\Program Files\Agilent\IO Libraries\intfcfg\intfcfg.txt (if you installed in the default location)Note:
If you are using Windows explorer to create intfcfg.ini, make sure that 'Hide File Extensions' is not set. If it is set, you will really be creating intfcfg.ini.txt, which will not work.Editing intfcfg.ini:
- Locate the [CfgNi488] section in the intfcfg.ini file.
- 'Uncomment' (by removing the leading semicolon) the appropriate GPIBn=yes line to force IO Config to recognize the NI-488 GPIB interface. Uncomment only the lines for which you have a configured NI-488 GPIB interface.
- Save the modified intfcfg.ini file.
- You can now run IO Config to configure the interface(s).
How to configure an Agilent GPIB card for use with National Instruments VISA
To use an Agilent GPIB card with NI-VISA, do the following (and be sure to reboot when prompted):
There are several known problems with NI-VISA version 2.5 when using the Agilent IO Libraries.
Preventing a naming conflict in NI-VISA (version 2.5):
For Agilent GPIB cards, NI-VISA will assign an Agilent GPIB card a VISA interface name of GPIBn where n is the trailing number of the SICL name assigned by the Agilent IO Config program. (e.g. hpib7 in SICL will translate to GPIB7 in NI-VISA.) If the SICL name does not have a trailing number, the n will be assigned from the logical unit number assigned by the Agilent IO Config program.
If Agilent VISA has configured an NI-488 GPIB card, it will normally default the SICL name to gpib0. The VISA Library Passport for Tulip will then map this back to NI-VISA as GPIB0. This will conflict with the GPIB0 that is already mapped to the NI-488 GPIB card in NI-VISA. This conflict will cause NI-VISA to not recognize the GPIB interface.
The work-around for this problem is to run Agilent IO Config and edit the SICL name for this card to something else to prevent the conflict (e.g. gpib10). This will then, for this example, map to GPIB10 in NI-VISA and not cause a conflict with GPIB0. Note, that although the GPIB10 interface is accessible from NI-VISA, it points indirectly (through Agilent SICL) to the same hardware as GPIB0. For this reason, your VISA programs should use GPIB0 and not GPIB10.
⌐ Copyright 2000 Agilent Technologies. All Rights Reserved.